21 matches found
CVE-2025-1558
CVE-2025-1558 affects Mattermost Mobile Apps (versions ≤ 2.25.0). The root cause is improper validation of GIF images prior to rendering, which allows a remote attacker to crash the Android app via a message containing a specially crafted GIF. The vulnerability is described across multiple source...
CVE-2025-30516
Summary of vulnerability (CVE-2025-30516) : Mattermost Mobile Apps versions ≤ 2.25.0 fail to terminate sessions upon logout under certain conditions (e.g., poor connectivity). This can allow unauthorized users on shared devices to access sensitive notification content via continued notifications....
CVE-2024-3872
Mattermost Mobile app versions 2.13.0 and earlier are affected by a vulnerability in the deep-link parsing logic, where a regular expression with polynomial complexity can be exploited by an unauthenticated remote attacker to freeze or crash the app via a long maliciously crafted link. The issue ...
CVE-2025-20036
CVE-2025-20036 affects Mattermost Mobile Apps, specifically versions
CVE-2025-21083
Mattermost Mobile Apps vulnerability CVE-2025-21083 affects Mattermost Mobile Apps versions
CVE-2024-24975
Mattermost Mobile: CVE-2024-24975 affects Mattermost Mobile before 2.13.0. The issue is uncontrolled resource consumption caused by the syntax highlighter not limiting the size of code blocks, which can crash the mobile app. Affected component is the syntax highlighter in Mattermost Mobile; root ...
CVE-2025-0476
Mattermost Mobile Apps (versions <= 2.22.0) are vulnerable due to improper handling of specially crafted attachment names, which can crash the mobile app for any user who opens a channel containing such an attachment. The issue is a denial-of-service-like crash rather than data disclosure. Aff...
CVE-2024-11358
Mattermost Android Mobile Apps (versions
CVE-2024-32945
Mattermost Mobile Apps (versions
CVE-2025-20630
Mattermost Mobile versions
CVE-2025-20072
Mattermost Mobile vulnerable: versions
CVE-2019-20852
Mattermost Mobile Apps prior to version 1.26.0 contain a local-logging issue where sensitive information (e.g., server addresses or message content) is not blocked from being written to device logs. The Red Hat/CVE entries confirm this description. Impact is stated as exposure of sensitive data t...
CVE-2019-20848
Mattermost Mobile Apps
CVE-2024-45833
Mattermost Mobile Apps <= 2.18.0 exposes passwords: the login autocomplete is not disabled when the password is typed and the visible password is selected, allowing the password to be saved in SwiftKey’s dictionary when a special character is used and masking is off. Affected: Mattermost Mobil...
CVE-2020-14449
Technical details are not publicly provided in the supplied documents. The materials mention Mattermost Mobile Apps before 1.30.0 and token disclosure to third-party servers, but no concrete guidance on affected components, exploit methods, or fixes is included. Monitor updates.
CVE-2024-39767
Mattermost Mobile Apps versions
CVE-2019-20850
Mattermost Mobile Apps before version 1.26.0 have a vulnerability where a view cache can persist on a device after logout. Affected product: Mattermost Mobile Apps. The provided documents do not detail the root cause, exploitability, or concrete impact beyond cache persistence. No remediation ste...
CVE-2020-14451
CVE-2020-14451 describes a flaw in Mattermost Mobile Apps (iOS) prior to version 1.29.0 where Single Sign-On cookies and Local Storage were not cleared on logout, potentially allowing access to residual authentication state after sign-out. The issue is due to the app not clearing SSO cookies/loca...
CVE-2019-20849
Mattermost Mobile Apps prior to version 1.26.0 have a cookie-clearing issue: cookie data can persist on the device after logout. Root cause indicated across sources is failure to clear cookies on logout, enabling possible exposure of prior session data. Impact aligns with partial confidentiality ...
CVE-2026-22880
Mattermost Mobile Apps (versions
CVE-2025-59480
Mattermost Mobile Apps (Android/iOS) versions up to and including 2.32.0 are affected by an insufficient verification of SSO redirect tokens. The root cause is failure to verify that SSO tokens originate from a trusted server, enabling a malicious Mattermost instance or an on-path attacker to obt...